Part Number Hot Search : 
212BJ N3053 D23C1 SDZ8V2D AQW210 SY100 S3BR10 CY7C006V
Product Description
Full Text Search
 

To Download TSS461C04 Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
 Features
* * * * * * * * * * * * * * * * * *
Fully Compliant to VAN Specification ISO/11519-3 Handles All Specified Module Types Handles All Specified Message Types Handles Retransmission of Frames on Contention and Errors 3 Separate Line Inputs with Automatic Diagnosis and Selection 1 Mbit/s Maximum Transfer Rate Normal or Pulsed (Optical and Radio Mode) Coding Intel(R), NEC(R), Texas Instruments(R) and Motorola(R) Compatible 8-bit Microprocessor Interface Multiplexed Address and Data Bus Idle and Sleep Modes 128 Bytes of General-purpose RAM DMA Capabilities for Message Handling 14 Identifier Registers with All Bits Individually Maskable 6-source Maskable Interrupt, Including an Interrupt-on-reset to Detect Glitches on the Reset Pin Integrated Crystal or Resonator Oscillator with Internal Baud Rate Generator and Buffered Clock Output Single +5V Power Supply 0.8 m CMOS Technology SO24 Package
VAN Data Link Controller TSS461C
Description
Cost optimization in car manufacturing is of extreme importance today. Solutions to this problem often implies the use of more advanced and intelligent electronic circuits. The TSS461C is a circuit which allows the transfer of all the status information needed in a car or truck over a single low-cost wire pair, that minimizes the electrical wire usage. It can be used to interconnect powerful functions (ABS, dashboard, power train control) and to control and interface car body electronics (lights, wipers, power window, etc.). The TSS461C is fully compliant with the ISO Standard 11519-3. This standard supports a wide range of applications such as low-cost remote-control switches. Typically it is used for lamp control; complex, highly-autonomous, distributed systems like engine controls, which require fast and secure data transfers. The TSS461C is a microprocessor-interfaced line controller for mid-to-high complexity bus-masters and listeners like injection/ignition control calculators, dashboard controllers and car stereo or mobile telephone CPUs. The microprocessor interface consists of a 256-bytes of RAM and a register area divided into 11 control registers, 14 channel register sets and 128 bytes of general purpose RAM, used as a message storage area, and a 6-source maskable interrupt. The circuit operates in RAM using DMA techniques, controlled by the channel and control registers. This allows virtually any microprocessor to interface with ease to the TSS461C, and to use the free RAM as a scratch pad. Messages are encoded in enhanced Manchester code, and an optional pulsed code for use with an optical or radio link, at a maximum bit rate of 1 Mbit/s. The TSS461C analyzes the messages received or transmitted according to 6 different criteria including some higher level checks. In addition, the bus interface has three separate inputs with automatic source diagnosis and selection, that allows for multibus listening or the automatic selection of the most reliable source at any time if several line receivers are connected to the same bus.
4193G-AUTO-12/04
1
Block Diagram
AD[7:0] ALE INT RESET TEST VCC GND
Address and Data Bus Multiplexing logic control bus data bus address bus status bus 128 bytes Message buffer RAM Protocol controller state machine and ID registers Status and control registers
Reception logic
Source diagnosis and selection logic
Data serializer and deserializer
CRC generator and checker
Clock generator and line synchronization logic
Transmission logic
XTAL1 XTAL2
CKOUT
TxD
RxD0 RxD1 RxD2
2
TSS461C
4193G-AUTO-12/04
TSS461C
Pin Configuration
TOP VIEW 24 Pin SOP AD4 AD5 AD6 AD7 VCC INT ALE (E) CS XTAL1 XTAL2 Test/VSS CKOUT Note: 1 2 3 4 5 6 7 8 9 10 11 12 24 23 22 21 20 19 18 17 16 15 14 13 AD3 AD2 AD1 AD0 VSS RESET TXD RXD0 RXD2 RXD1 WR (R/W) RD (VSS)
1. The names in parenthesis refer to the functionalities in Motorola mode.
I/O Type
Pin Name AD0 AD1 AD2 AD3 AD4 AD5 AD6 AD7
Pin Number 21 22 23 24 1 2 3 4 7 13 14 8 6
Pin Function
I/O TTL
Multiplexed address and data bus. The address is latched on the falling address of ALE.
I Trigger TTL
ALE RD (VSS) WR (R/W) CS(E)
Address Latch Enable Read Command Write Command Chip Select (active high) Interrupt Asynchronous general reset glitch filtered (12 ns)
Open-drain I Trigger CMOS Pull-down
INT
RESET
19
3
4193G-AUTO-12/04
I/O Type
Pin Name RXD0 RXD1 RXD2
Pin Number 17 15 16 18 9 10 12 11 5 20
Pin Function
I CMOS Pull-down
VAN bus Inputs
3-state I 0 0 Ground Power Ground
TXD XTAL1 XTAL2 CKOUT TEST/VSS VCC VSS
VAN bus Output Crystal oscillator or clock input pins Buffered clockout output enabled if no reset Oscillator Ground +5V Power Supply
4
TSS461C
4193G-AUTO-12/04
TSS461C
Operation
The TSS461C is a microprocessor-controlled line controller for the VAN bus. It can interface to virtually any microprocessor, but the I/O signals of the circuit have been optimized to use with the TSC51/TSC251 series of microcontrollers. It features a multiplexed address and data bus, controlled by an address strobe pin ALE and separated read RD and write WR command pins. The address is latched on the falling edge of ALE. The circuit also features one single interrupt pin. This pin can be treated as level or edge sensitive, For example, if there is a pending interrupt inside the circuit when another interrupt is reset, the INT pin will emit a high pulse with the same pulse width as the internal write strobe (typically 20 ns). Figure 1. Typical Application
VAN Bus
Remaining Pins
General I/O
TSS461C Series Microcontroller
C1
33 pF
DATA
P3.6/WR P3.7/RD ALE
WR RD
TXD
Differential
+
RXD0
ALE
P0.7 P0.6 P0.5 P0.4 P0.3 P0.2 P0.1 P0.0 RESET XTAL1 INT VCC
AD7 AD6 AD5 AD4 AD3 AD2 AD1 AD0
VAN DLC
RXD1 RXD2
DATA
+
-
VREF
CS
DATA
+
VAN Line Driver & Receivers
INT CKOUT RESET
DATA
GND
XTAL1
XTAL2
GND
5
4193G-AUTO-12/04
Microprocessor Interface
Interface Modes
The processor controls the TSS461C by reading and writing the internal registers of the circuit. These registers appear to the processor as regular memory locations. The TSS461C must be plugged in an Intel or Motorola environment with an 8-bit address/data bus multiplexed. Table 1. Access Mode Logic
CS (E) 0 1 1 1 1 0 0 1 1 0 1 0 1 RD WR (R/W)
Operation Mode No operation Write Operation in Motorola mode Read operation in both modes Write operation in Intel mode No operation
In Intel environment, access operations need CS active, a read one with RD active, a write one with WR active. If TSS461C is the single peripheral in the processor space, CS can be wired to VCC. In Motorola environment, the RD pin is wired to VSS and the access operations are driven by CS (E). Contrary to Intel mode, CS (E) must never be wired to VCC even if the TSS461C is alone. To switch on-the-fly from one mode to the other, CS must be inactive. Intel Mode The Intel mode interface consists of 13 pins. 8 pins are the multiplexed address and data bus, and the rest are the address strobe, the read and write commands, the chip select and the interrupt request pins. To access the memory locations in Intel mode, the processor must first assert a valid address on the multiplexed address and data bus and drive the address strobe pin high. When the required setup time has passed, the processor must drive the address strobe low, and keep the address valid for the required hold time. The processor must then either assert the data to be written on the address and data bus, if a write is intended, or float the data bus for a read. The next step is to drive either the write or read command pins low, according to the function required, and at the same time drive the chip select pin high. The TSS461C access cycle is then terminated by driving the chip select and command pins low.
Note: that the chip select pin may be driven high for the entire access cycle, and may also remain high during and after the termination of the cycle.
6
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 2. Intel Read and Write Cycles
ALE
DATA TO BE WRITTEN DATA READ
AD[7:0]
ADDRESS
ADDRESS
RD
WR
CS WRITE CYCLE READ CYCLE
Motorola Mode
In Motorola mode, the WR pin becomes the R/W command, the RD pin must be connected to ground and the CS pin becomes the E strobe. There is no separate chip select input. For example, if some external decoder is used, this decoder should not drive the E input high unless the processors E output is high as well. See Figure 3 for the Motorola read and write cycles. The main difference between Intel and Motorola mode is that the timing in Intel mode is referenced to the command signals (RD and WR), but in Motorola mode the reference is the E signal. Figure 3. Motorola Read and Write Cycles
ALE
DATA TO BE WRITTEN DATA READ
AD[7:0]
ADDRESS
ADDRESS
VSS (RD)
R/W (WR)
E (CS) WRITE CYCLE READ CYCLE
Interrupts
If an event occurs in the TSS461C that needs the attention of the processor, this will be signalled on the active low, open-drain interrupt request pin. The events that create this request are controlled by the internal registers. Every time the microprocessor accesses any of the interrupt registers (addresses 0x08 to 0x0B), the INT pin will be released momentarily. This enables the TSS461C to work with processors that either have edge or level sensitive interrupt inputs.
7
4193G-AUTO-12/04
Reset
The reset is applied asynchronously regarding XTAL clock. It can be done either by the RESET pin or by software. The RESET pin is a CMOS trigger input with a pull-down resistor (110 k). An external 1 F capacitor to VCC provides to RESET pin an efficient behavior. The software reset is made through the GRES command bit of the Command Register (0x03). The two resets are ored, filtered and gauged. Then the internal reset, always asserted asynchronously, enables the internal oscillator. Then it waits for eight clock periods for the oscillator stability. The different blocks of the TSS461C need to be turned on synchronously. So the release of the internal reset is synchronous and a loose clock can let the TSS461C in permanent reset after applying Reset.
8
TSS461C
4193G-AUTO-12/04
TSS461C
Oscillator
An oscillator is integrated in the TSS461C, and consists of an inverting amplifier which the input is XTAL1 and the output XTAL2. A parallel resonance quartz crystal or ceramic resonator must be connected to these pins. As shown in Figure 1, two capacitors have to be connected from the crystal pins to ground. The values of C1 depend on the frequency chosen and can be selected using the graphic given in Figure 33. If the oscillator is not used, then a clock signal must be fed to the circuit via the XTAL1 input. Note, that this pin will behave as a CMOS level compatible Schmitt trigger input. In this case, the XTAL2 output should be left unconnected. The oscillator also features a buffered clock output pin CKOUT. The signal on this pin is directly buffered from the XTAL1 input, without inversion. There is one more pin used for the oscillator. The TEST/VSS pin is in fact its ground, and unless this pin is firmly connected to ground, with decoupling capacitors, the oscillator will not operate correctly. The test mode itself, i.e., when the TEST/VSS pin is held high, is only intended for factory use, and the functionality of this mode is not specified in any way. Furthermore, it is subject to change without notice, the only exception is for incoming inspection tests using the test program. The clock signal is then fed to the clock generator generate all the necessary timing signals for the operation of the circuit. The clock generator is controlled by a 4-bit code called the clock divider.
FXTAL1 F TSCLK = -----------------n x 16
9
4193G-AUTO-12/04
Table 2. Clock Divider
8 MHz Clock Divider 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 Divide by 1 2 4 8 16 32 64 128 1.5 3 6 12 24 48 96 192 KTS/s 500 250 125 62.5 31.25 15.625 7.813 3.906 333.333 166.666 83.333 41.666 20.833 10.416 5.208 2.604 Kbits/s 400 200 100 50 25 12.5 6.25 3.125 266.666 133.333 66.666 33.333 16.666 8.333 4.166 2.083 KTS/s 375 187.50 93.75 46.875+ 23.438 11.718 5.859 500 250 125 62.50 31.25 15.625 7.813 3.906 1.953 6 MHz Kbits/s 300 150 75 37.5 18.75 9.375 4.688 400 200 100 50 25 12.50 6.25 3.125 1.5625 KTS/s 250 125 62.50 31.25 15.625 7.813 3.906 1.953 166.666 83.333 41.666 20.833 10.416 5.208 2.604 1.302 4 MHz Kbits/s 200 100 50 25 12.5 6.25 3.125 1.562 133.333 66.666 33.333 16.666 8.333 4.166 2.083 1.042 KTS/s 125 62.50 31.25 15.625 7.813 3.906 1.953 166.666 83.333 41.666 20.833 10.416 5.208 2.604 1.302 0.651 2 MHz Kbits/s 100 50 25 12.5 6.25 3.125 1.562 133.333 66.666 33.333 16.666 8.333 4.166 2.083 1.042 0.521
10
TSS461C
4193G-AUTO-12/04
TSS461C
VAN Protocol
Line Interface
There are three line inputs and one line output available on the TSS461C. The three inputs are either programmed by software or automatically selected by a diagnosis system. The diagnosis system continuously monitors the data received through the three inputs, and compares them and the selected bitrate. It then chooses the most reliable input according to the results. The data on the line is encoded according to the VAN standard ISO/11519-3. This means that the TSS461C is using a two-level signal having a recessive (1) and a dominant (0) state. Furthermore, due to the simple medium used, all data transmitted on the bus is also received simultaneously. Consequently, the VAN protocol is a CSMA/CD (Carrier Sense Multiple Access/Collision Detection) protocol, allowing for continuous bitwise arbitration of the bus, and nondestructive (for the higher priority message) collision detection. Figure 4. CSMA/CD Arbitration
Arbitration field
Node a: TxD Node b: TxD Node c: TxD On Bus: DATA
R D R D R D
2
Node a loses the arbitration Node a releases the bus
3
Node b wins the arbitration
1
Node c loses the arbitration Node c releases the bus
R D
R: Recessive Level
D: Dominant Level
In addition to the VAN specification there is also a pulsed coding of the dominant and recessive states. This mode is intended to be used with an optical or radio link. In this mode, the dominant state for the transmitter is a low pulse, (2x prescaled clocks at the beginning of the bit) and the recessive state is just a high level. When receiving in this mode, it is not the state of the signal which is decoded, but the edges. Also, reception is imposed on the RxD0 input, and the diagnosis system does not operate correctly. In addition, in this mode there is an internal loopback in the circuit since optical transceivers are not able to receive the signal that they transmit.
11
4193G-AUTO-12/04
In Figure 5 the pulsed waveforms are shown. In Figure 8 through Figure 14 the low "timeslots" (i.e. blocks of 16 prescaled clocks) should be replaced by the dominant waveform showed in Figure 5, to obtain the correct representations for pulsed coding. Figure 5. State Encoding
VAN BUS SEQUENCE
NORMAL OR PULSED RECESSIVE ST ATE
VAN BUS SEQUENCE
NORMAL DOMINANT STATE
VAN BUS SEQUENCE
PUSED DOMINANT STATE
NUMBER OF PRESCALED CLOCKS
0
2
4
6
8
10
12
14
16
VAN Frame
Figure 6. VAN Bus Frame
Identifier Field Command EXT RAK R/W RTR Data Field Frame Check Sum
SOF
EOD
ACK
EOF
The VAN bus supports three different module (unit) types: 1. The Autonomous module, which is a bus master. It can transmit Start Of Frame (SOF) sequences, it can initiate data transfers and can receive messages. 2. The Synchronous access module. It cannot transmit SOF sequences, but it can initiate data transfers and can receive messages. 3. The Slave module, which can only transmit using an in-frame mechanism and can receive messages. Figure 7. Hierarchical Access Methods
Autonomous Rank 0 SOF ID Synchronous Rank 1 ID COM Slave
RTR
COM
DATA
FCS
EOD ACK
EOF
DATA
FCS
EOD ACK
EOF
Rank 16
DATA
FCS
EOD ACK
EOF
12
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 6 shows a normal VAN bus frame. It is initiated with a Start of Frame (SOF) sequence shown in Figure 8. The SOF can only be transmitted by an autonomous module. During the preamble, the TSS461C will synchronize its bit rate clock to the data received. Figure 8. Framing Sequences
VAN BUS START SYNC
PREAMBLE SEQUENCE START OF FRAME
VAN BUS SEQUENCE END OF DATA ACK END OF FRAME
NUMBER OF PRESCALED CLOCKS
0
16
32
48
64
80
96
112 128 144
160 176 192
When the complete SOF sequence has been transmitted or received, the circuit will start the transmission or reception of the identifier field. All data on the VAN bus, including the identifier and Frame Check Sum (FCS), are transmitted using enhanced Manchester code. In enhanced Manchester code, three NRZ bits are transmitted first followed by one Manchester bit, then three more NRZ bits followed by one Manchester bit and so on. Since the high state is recessive and the low state is dominant, the bus arbitration can be done. If a module wants access to the bus, it must first listen to the bus during one full End of Frame (EOF) and one full Inter Frame Spacing (IFS) period, to determine whether the bus is free or not (i.e., no dominant states received). Figure 9. Data Encoding
VAN BUS SEQUENCE
NRZ 0
NRZ 1
VAN BUS SEQUENCE
MANCHESTER 0
VAN BUS SEQUENCE
MANCHESTER 1
NUMBER OF PRESCALED CLOCKS 0 8 16 24 32
13
4193G-AUTO-12/04
The IFS is defined to be a minimum of 64 prescaled clocks periods. The TSS461C, accepts an IFS of zero prescaled clocks for the reception only of a SOF sequence. Once the bus is free, the module must now, if it is an autonomous module emits a SOF sequence or, if it is a synchronous access module, wait until it detects a preamble sequence. Until this point there can be several modules transmitting on the bus, and there is no possibility of knowing if this is the case or not. Therefore, the first field in which arbitration can be performed is the identifier field. Since the logical zeroes on the bus are dominant, and all data is transmitted with the most significant bit (MSB) first, the first module to transmit a logical zero on the bus will be the prioritized module, i.e., the message that is tagged with the lowest identifier will have priority over the other messages. However it is possible that two messages transmitted on the bus will have the same identifier. The TSS461C therefore, continues the arbitration of the bus throughout the whole frame. In addition, if the identifier in transmission has been programmed for reception as well, it transmits and receives messages simultaneously, right up till the Frame Check Sequence (FCS). Only then, if the TSS461C has transmitted the whole message. It discards the message received. Arbitration loss in the FCS field is considered as a CRC error during transmission. This feature is called full data field arbitration, and it enables the user to extend the identifier. For instance, it can be used to transmit the emitting modules address in the first bytes of the data field, thus enabling the identifier to specify the contents of the frame and the data field to specify the source of the information. The identifier field of the VAN bus frame is always 12 bits long, and it is always followed by the 4-bit command field: * The first bit of the command is the extension bit (EXT). This bit is defined by the user on transmission and is received and retained by the TSS461C. To conform with the standard, it should be set to 1 (recessive) by the user, else the frame is ignored without any IT generation. The second bit is the request ACKnowledge bit (RAK). If this bit is a logical one, the receiving module must acknowledge the transfer with an in-frame acknowledgement in the ACK field. If it is set to logical zero, then the ACK field must contain an acknowledge absent sequence. The third bit is the Read/Write bit (R/W). This bit indicates the direction of the data in a frame. - - If set to zero it is a "write" message, i.e. data transmitted by one module to be received by another module. If it is set to one it implies a "read" message, i.e., a request that another module should transmit data to be received by the one that requested the data (reply request message).
*
*
*
Last in the command field is the Remote Transmission Request bit (RTR). This bit is a logical zero if the frame contains data and a logical one if the frame does not contain data. In order to conform with the standard a received frame included the combination R/W. RTR = 01 is ignored without any IT generation.
All the bits in the command field are automatically handled by the TSS461C, so the user doesn't need to be concerned for encoding and decoding these bits. The command bits transmitted on the VAN bus are calculated from the current status of the active message.
14
TSS461C
4193G-AUTO-12/04
TSS461C
After the command field comes the data field. This is just a sequence of bytes transmitted, MSB first. In the VAN standard, the maximum message length is set to 28 bytes, but the TSS461C handles messages up to 30 bytes. The next field is the FCS field. This field is a 15-bit CRC checksum defined by the following generator polynomial g(x) of order 15: g(x) = x15 + x11 + x10 + x9 + x8 + x7 + x4 + x3 + x2 + 1 The division is done with a rest initialized to 0x7FFF, and an inversion of the CRC bits is performed before transmission. However, since the CRC is calculated automatically from the identifier, command and data fields by the TSS461C, the user should not be concerned with the circuit. When the frame check sequence has been transmitted, the transmitting module must transmit an End Of Data (EOD) sequence, followed by the ACKnowledge field (ACK) and the End of Frame sequence (EOF) to terminate the transfer. Figure 10. Acknowledge Sequences
VAN BUS SEQUENCE
POSITIVE ACKNOWLEDGE
VAN BUS SEQUENCE
ABSENT ACKNOWLEDGE
NUMBER OF PRESCALED CLOCKS
0
8
16
24
32
Frame Examples
The frames transmitted on the VAN bus are generated by several modules, each supplying different parts of the message. Figure 11 through Figure 14 show the four frame types specified in the VAN standard, and what module is generating the different fields. * The most straightforward frame is the normal data frame in Figure 11. Like all other frames it is initiated with a SOF sequence. This sequence is generated by a bus master (not shown in the figure). During this frame, there is basically only one module transmitting with the exception of the acknowledgement, generated by the receiving module if requested in the RAK bit. The reply request frame with immediate reply in Figure 12 is the only frame in which a slave module can transmit data by filling it into the appropriate field. The difference for the frame on the bus is that the R/W bit has changed state compared to the normal frame. This is a highly interactive frame where a bus master generates the SOF and the initiator generates the identifier, the three first bits of the command, and the acknowledge. The RTR bit, the data field, the frame check, the EOD and the EOF are all generated by the replying module. The reply request frame with deferred reply in Figure 13 is the same frame as the reply request frame with immediate reply. But since the requested module does not
*
* * *
*
15
4193G-AUTO-12/04
generate the RTR bit, the requesting module will continue with the frame check, the EOD and the EOF. * * During this frame, the requested module will only generate the acknowledge, and only if this was requested by the initiator through the RAK bit. Finally, the deferred reply frame in Figure 14, which is sent when a module has prepared a reply for a reply request that has been received earlier. This frame is similar to the normal data frame with the exception being the R/W bit that has changed state.
Figure 11. Normal Data Frame
With Acknowlegment
EXT RAK R/W RTR (*) EOD ACK ACK ACK ACK ACK EXT RAK R/W RTR (*) SOF IDENTIFIER DATA CRC EOD EOF
TRANSMITTING Module
SOF
IDENTIFIER
DATA
CRC
EOF
RECEIVING Module
FRAME on Bus
EXT : Recessive from Transmitter RAK: Recessive for acknowledge from Transmitter R/W : Dominant from Transmitter RTR : Dominant from Transmitter - (*) Manchester bit ACK : Positive from Receiver because RAK is Recessive
Without Acknowlegment
EXT RAK R/W RTR (*) EOD
TRANSMITTING Module
SOF
IDENTIFIER
DATA
CRC
EOF
RECEIVING Module
EXT RAK R/W RTR (*)
FRAME on Bus
SOF
IDENTIFIER
DATA
CRC
EOD
EOF
EXT : RAK: R/W : RTR : ACK :
Recessive from Transmitter Dominant for no acknowledge from Transmitter Dominant from Transmitter Dominant from T ransmitter - (*) Manchester bit Absent from Transmitter and from Receiver because RAK is Dominant
16
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 12. Reply Request Frame with Immediate Reply
EXT RAK R/W RTR (*)
REQUESTING Module
SOF
IDENTIFIER
RTR (*)
EOD
REQUESTED Module
DATA
CRC
ACK ACK
ACK
EOF DATA CRC
EXT RAK R/W RTR (*)
FRAME on Bus
SOF
IDENTIFIER
EOD
EOF
EXT : RAK : R/W : RTR : ACK :
Recessive from Requestor Recessive for acknowledge from Requestor Recessive from Requestor Recessive from Requestor and Dominant from Requestee (*) Manchester bit Absent from Requestee and Positive from Requestor because RAK is Recessive
Figure 13. Reply Request Frame with Deferred Reply
EXT RAK R/W RTR (*) EOD
REQUESTING Module
SOF
IDENTIFIER
CRC
ACK ACK ACK
EOF
REQUESTED Module
EXT RAK R/W RTR (*)
FRAME on Bus
SOF
IDENTIFIER
CRC
EOD
EOF
EXT : RAK : R/W : RTR : ACK :
Recessive from Requestor Recessive for acknowledge from Requestor Recessive from Requestor Recessive from Requestor - (*) Manchester bit Absent from Requestor and Positive from Requestee because RAK is Recessive
17
4193G-AUTO-12/04
Figure 14. Deferred Reply Frame
EXT RAK R/W RTR (*) EOD
REPL YING module
SOF
IDENTIFIER
DATA
CRC
ACK ACK ACK
EOF
RECEIVING module
EXT RAK R/W RTR (*)
FRAME
on bus
SOF
IDENTIFIER
DATA
CRC
EOD
EOF
EXT RAK R/W RTR ACK
: : : :
Recessive from Replyer Recessive for acknowledge from Replyer Recessive from Replyer Dominant from Replyer - (*) Manchester bit : Absent from Replyer and Positive from Receiver because RAK is Recessive
18
TSS461C
4193G-AUTO-12/04
TSS461C
Diagnosis System
The purpose of the diagnosis system is to detect any short or open circuits on either the DATA or DATA lines and to permit, if it is possible, to carry the communications on the non-defective line. The diagnosis system is based on the assumption that three separate line receivers are connected to the VAN bus (see Figure 3): * * One of the line receivers is connected in differential mode, sensing both DATA and DATA signals, and is connected to the RxD0 input. The other two line receivers are operating in single wire mode and are sensing only one of the two VAN bus signals: - - The line receiver sensing DATA is connected to RxD1 The line receiver sensing DATA is connected to RxD2
The diagnosis system analyzes and compares the data sent over both VAN lines. So, the diagnosis system executes a digital filtering and transition analyses. In order to perform its investigation, three internal signals are generated, RI (Return to Idle), SDC (Synchronous Diagnosis Clock) and TIP (Transmission In Progress). One of four operating modes can be chosen to manage the results of the diagnosis system.
Diagnosis States
If the diagnosis system finds a failure on any of the VAN bus signals, it changes from nominal to degraded mode, and connects the line receiver not coupled to the failing signal to the reception logic. When the diagnosis system finds that the failing signal is working again, it returns to nominal mode and re-connects the differential line receiver to the reception logic. A major error occurs when both the VAN bus signals fail.
Figure 15. Diagnosis States
Nominal
Major Error Degraded Data Degraded Data
- Failure during the frame. - Default of transitions on the valid input between 2 consecutive SDC rising edges. - Protocol fault - In specified selection mode, every RI pulse when an EOF is detected or through an active SDC. - In automatic selection mode and SDC active, no failure sampled by 2 consecutive SDC rising edges. - General reset.
19
4193G-AUTO-12/04
Status bits give permanent information on the diagnosis performed, whatever the programmed operating mode. This is encoded over three bits: Sa, Sb and Sc. Sa and Sb bits indicate the four possible states of the VAN bus. Table 3. Status Bits Sa and Sb
Sa 0 Sb 0 Mode Fault Status 0 1 Mode Fault Status 1 0 Mode Fault Status 1 1 Mode Fault Status Communication Nominal No fault on VAN bus Differential communication DATA and DATA Degraded on DATA Fault on DATA Communication on DATA Degraded on DATA Fault on DATA Communication on DATA Major error Fault on DATA and DATA No communication on DATA and DATA (attempt to communicate alternatively on DATA then DATA every SDC period.
Notes:
1. Sc bit sets to 1 as soon as one of the three inputs (RXD2, RXD1, RXD0) differs from the others in the input comparison analysis performed by the diagnosis system, S2 is set. 2. The only way to reset this status bit is through the RI signal or a general reset.
Internal Operations
Digital Filtering If several spurious pulses occur during one bit, the diagnosis for defective conductor may occur. To avoid such errors, digital filters are implemented. Filtering operation is based on sampling of the comparator output signals. A transition is taken into account only if it is observed over five samples (1/16th of timeslot). Transition Analyses These analyses are continuously done on the effective edges on comparators after digital filtering. * Asynchronous diagnosis: The asynchronous diagnosis is done by comparing the number of edges on DATA and DATA. If four edges are detected on one input and no edges on the other during the same period, the second input is considered faulty and the diagnosis mode will change to one of the degraded modes. Synchronous diagnosis: The synchronous diagnosis counts the number of edges on the data input connected to the reception logic during one SDC period.
*
20
TSS461C
4193G-AUTO-12/04
TSS461C
If there are less than four edges during one SDC period, the diagnosis mode will change to the major error mode. * Transmission diagnosis: The transmission compares RxD1 and RxD2 inputs (through the input comparators and the filters) with the data transmitted on TxD output. At a time when the transmission logic generates a dominant (recessive transition), the inputs can give different values. Taking into account the filtering delay, the bus line seen as dominant is assumed to be correct, the other one, recessive, is considered faulty. The diagnosis mode is changed to reflect that. Protocol fault: The protocol fault is detected by counting the number of consecutive dominant timeslots. If eight consecutive timeslots are dominant, the diagnosis mode will change to the major error mode.
*
Generation of Internal Signals
RI Signal (Return to Idle) This signal is used to return to nominal mode in the three specified selection modes (see Section "Diagnosis States" and Section "Programming Modes"). The RI signal is disabled in automatic selection mode. The RI signal is a pulse generated when an EOF is detected. So, at the end of each frame, regarding the diagnosis status bit Sa, Sb & Sc, the user can select its own choice. SDC Signal (Synchronous Diagnosis Clock) This time base is used by diagnosis system in automatic selection mode (see Section "Programming Modes") when no event is recorded on the bus. The SDC is generated either by a special SDC divider connected to the timeslot clock, or manually. The SDC clock period must be longer compared to the timeslot duration. A typical SDC period should be greater than the maximum frame length appearing on the VAN network. TIP Signal (Transmission in Progress) This signal must be enabled to allow the transmission diagnosis (see Section "Transition Analyses"). The TIP turns on synchronously at the beginning of the transmission: * * * * * * For asynchronous bus access, the beginning of SOF; For synchronous bus access, the beginning of the identifier field; and For a request of in frame reply, the RTR bit of the command field. after EOF; after a losing of arbitration or a code violation detection; and for a requester of in frame reply, when the arbitration is lost on RTR the bit.
The TIP turns off synchronously at the end of the transmission:
This signal is not generated when the transmission logic only sends an ACK.
21
4193G-AUTO-12/04
Programming Modes
Four programming modes determine how to use the three different inputs and the diagnosis system. * * 3 specified selection modes 1 automatic selection mode
Table 4. Programming Modes
Ma 0 0 1 1 Mb 0 1 0 1 Operating Mode Differential communication Degraded communication on RxD2 (DATA) Degraded communication on RxD1 (DATA) Automatic selection according to the diagnosis status
22
TSS461C
4193G-AUTO-12/04
TSS461C
Registers
Mapping
Figure 16. Memory Map
0x78 to 0x7F (r/w) 0x70 to 0x77 (r/w) 0x68 to 0x6F (r/w) 0x60 to 0x67 (r/w) 0x58 to 0x5F (r/w) 0x50 to 0x57 (r/w) 0x48 to 0x4F (r/w) 0x40 to 0x47 (r/w) 0x38 to 0x3F (r/w) 0x30 to 0x37 (r/w) 0x28 to 0x2F (r/w) 0x20 to 0x27 (r/w) 0x18 to 0x1F (r/w) 0x10 to 0x17 (r/w) 0x0C to 0x0F 0x0B (w) 0x0A (r/w) 0x09 (r) 0x08 0x07 (r) 0x06 (r) 0x05 (r)
The TSS461C memory map consists of three different areas, the Control & Status registers, the Channel Registers and the Message Data (or Mailbox).
Channel13 Channel 13
Channel 12 Channel 11 Channel 10 Channel 9 Channel 8 Channel 7 Channel 6 Channel 5 Channel 4 Channel 3 Channel 2 Channel 1 0x17 (r/w) 0x17 (r/w) 0x7F (r/w) 0x7E (r/w)
0xFF
Data Byte 127
ID_Mask [3..0] ID_Mask [11..4]
0x7C & 0x7D Reserved Reserved 0x7B (r/w) Message Length + Status 0x7A (r/w) DRAK + Message Address 0x79 (r/w) ID_TAG (lsb) + COM 0x78 (r/w) ID_TAG (msb)
Channel 13 Registers
ID_Mask [3..0]
0x16 (r/w) ID_Mask[11..4] ID_Mask [11..4] 0x14 & 0x15 Reserved 0x13 (r/w) Message Length + Status 0x12 (r/w) DRAK + Message Address 0x11 (r/w) ID_TAG [3..0] + COM 0x10 (r/w) ID_TAG [11..4]
Channel 0 Registers
Channel 0
Reserved Interrupt Reset Interrupt Enable (0x80) Interrupt Status (0x80) Reserved Last Error Status (0x00) Last Message Status (0x00) Transmit Status (0x00) 0x8C 0x8B 0x8A 0x89 0x88 0x87 0x86 0x85 0x84 0x83 0x82 0x81 0x80 Data Byte 12 Data Byte 11 Data Byte 10 Data Byte 9 Data Byte 8 Data Byte 7 Data Byte 6 Data Byte 5 Data Byte 4 Data Byte 3 Data Byte 2 Data Byte 1 Data Byte 0
Line Status (0bx01xxx00) 0x04 (r) Command (0x00) 0x03 (w) 0x02 (r/w) Diagnosis Control (0x00) 0x01 (r/w) Transmit Control (0x02) Line Control (0x00) 0x00 (r/w)
Register
Notes:
Message
1. All the non-specified addresses between 0x00 and 0x7F are considered as absent. 2. (r) means read-only register. (w) means write-only register. (r/w) means read/write register. 3. Value after RESET is found after register name. If no value is given, the register is not initialized at RESET.
23
4193G-AUTO-12/04
Control and Status Registers
Line Control Register (0x00)
7 MR3 6 MR2 5 MR1 4 MR0 3 VER2 2 VER1 1 VER0 0 MT
* * *
Read/write register. Default value after reset: 0y00 reserved: Bit 2, this bit cannot be set by the user; a 0 must always be written to this bit.
CD[3:0] Clock Divider
They control the VAN Bus rate through a Baud Rate generator according to the following formula:
FXTAL1 F TSCLK = -----------------n x 16
PC Pulsed CodeOne
The TSS461C will transmit and receive data using the pulsed coding mode (i.e optical or radio link mode). The use of this mode implies communication via the RXD0 input and the non-functionality of the diagnosis system. Zero: (Default at Reset). The TSS461C will transmit and receive data using the Enhanced Manchester code (RXD0, RXD1, RXD2).
IVTX IVRX
Invert TXD output. Invert RXD inputs.The user can invert the logical levels used on either the TXD output or the RXD inputs in order to adapt to different line drivers and receivers. One: A one on either of these bits will invert the respective signals. Zero: (Default at Reset). The TSS461C will set TXD to recessive state in Idle mode and consider the bus free (recessive states on RXD inputs).
Transmit Control Register (0x01)
7 MR3
6 MR2
5 MR1
4 MR0
3 VER2
2 VER1
1 VER0
0 MT
* *
Read/Write register Default value after reset: 0x02
24
TSS461C
4193G-AUTO-12/04
TSS461C
MR[3:0]: Maximum Retries These bits allow the user to control the amount of retries the circuit will perform if any errors occurred during transmission. Table 5. Retries
MR [3:0] 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 Max Number of Retries 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Max Number of Transmits 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16+
Note:
Bus contention is not regarded as an error and an infinite number of transmission attempts will be performed if bus contention occurs continuously.
VER[2:0]: DLC Version After Reset
* *
000: TSS461A & B 001: TSS461C and TSS461C
These bits cannot be set by user; 001 must always be written to these bits.
MT: Module Type
The three different module types are supported (see Section "VAN Frame"): One: The TSS461C is an autonomous module (Rank 0), an synchronous access module (Rank 1) or a slave module (Rank 16). Zero: The TSS461C is an synchronous access module (Rank 1) or a slave module (Rank 16).
Diagnosis Control Register (0x02)
7 SDC3
6 SDC2
5 SDC1
4 SDC0
3 Ma
2 Mb
1 ETIP
0 ESDC
* *
Read/Write register Default value after reset: 0x00
25
4193G-AUTO-12/04
The diagnosis is discussed in detail in Section "Diagnosis States". * * * In its four high order bits the user can program the SDC rate SDC [3:0] In its two medium order bits the diagnosis system mode is controlled: M1, M0 In the two low order bits, the user controls if the SDC and TIP are to be generated automatically ETIP, ESDC
SDC [3:0]: SDC Divider
The input clock is the times lot clock. Table 6. System Diagnosis Clock Divider
SDC Divider SDC [3:0] 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 Divide By 64 128 256 512 1024 2048 4096 8192 16384 32768 65536 131072 262144 524288 1048576 2097152
Ma, Mb: Operating Mode Command Bits
Table 7. Diagnosis System Command Bits
Ma 0 0 1 1 Mb 0 1 0 1 Forces the Communication on RxD0 (differential) Forces the Communication on RxD2 (DATA) Forces the Communication on RxD1 (DATA) Automatic selection
ETIP: Enable Transmission In Progress
One: Enable TIP generation Zero: Disable TIP generation.
26
TSS461C
4193G-AUTO-12/04
TSS461C
* The Transmission In Progress (TIP) tells the diagnostic system to enable transmission diagnosis.
ESDC: Enable System Diagnosis Clock
One: Enable SDC divider. Zero: Disable SDC divider. * The Synchronous Diagnosis Clock (SDC) controls the cycle time of the synchronous diagnosis.
Command Register (0x03)
7 GRES 6 SLEEP 5 IDLE 4 ACTI 3 REAR 2 0 1 0 0 MSDC
* * *
Write only register. Reserved: Bit 1, 2. These bits cannot be set by the user; a zero must always be written to these bit. If the circuit is operating at low bit rates, there might be a considerable delay between the writing of this register and the performing of the actual command (worst case 6 timeslots). The user must verify, by reading the Line Status Register (0x04), that the commands have been performed.
GRES: General Reset
The Reset circuit command bit performs, if set, exactly as if the external reset pin was asserted. This command bit has its own auto-reset circuitry. One: Reset active Zero: Reset inactive
SLEEP: Sleep Command
If the user sets the Sleep bit, the circuit will enter sleep mode. When the circuit is in sleep mode, all non-user registers are setup to minimize power consumption and the oscillator is stopped. To exit from this mode, the user must set either the idle or activate commands. One: Sleep active Zero: Sleep inactive
27
4193G-AUTO-12/04
IDLE: Idle Command
If the user sets the Idle bit, the circuit will enter idle mode. In idle mode the oscillator will operate, but the TSS461C will not transmit or receive anything on the bus, and the TXD output will be in three-state One: Idle active Zero: Idle inactive
ACTI: Activate Command
The Activate command will put the circuit in the active mode, i.e it will transmit and receive normally on the bus. When the circuit is in activate mode the TXD three-state output is enabled. One: Activate active Zero: Activate inactive
REAR: Re-Arbitrate Command
This command will, after the current attempt, reset the retry counter and re-arbitrate the messages to be transmitted in order to find the highest priority message to transmit. One: Re-arbitrate active Zero: Re-arbitrate inactive
MSDC: Manual System Diagnosis Clock
Rather than using the SDC divider described in Section "Diagnosis Control Register (0x02)", the user can use the manual SDC command to generate a SDC pulse for the diagnosis system. This MSDC pulse should be high at least two timeslot clock.
Line Status Register (0x04)
7 x 6 SPG 5 IDG 4 Sc 3 Sb 2 Sa 1 TXG 0 RXG
Read only register. * * Default value after reset: 0bx01xxx00. This register reports the operation mode of the TSS461C in the Sleep an Idle bits (Command Register located at address 0y03) as well as the diagnosis system status bits S2 to S0 discussed in Section "Diagnosis System".
SPG: Sleeping IDG: Idling Default mode at reset
Sa, Sb and Sc
Diagnosis system status bits * Sa and Sb
28
TSS461C
4193G-AUTO-12/04
TSS461C
Table 8. Diagnosis System Status Bits
Sb 0 0 1 1 Sa 0 1 0 1 Communication Indication Nominal mode, differential communication Degraded over DATA, fault on DATA Degraded over DATA, fault on DATA Major error, fault on DATA and DATA
*
Sc: As soon as one of the three inputs (RXD2, RXD1, RXD0) differs from the others in the input comparison analysis perform by the diagnosis system, S2 is set. The only way to reset this status bit is through the RI signal or a general reset.
TXG: Transmitting
If this status bit is active, it indicates that the TSS461C has chosen an identifier to transmit, and it will continue to make transmission attempts for this message until it succeeds or the retry count is exceeded. The receiving indicates that there is activity on the bus.
Note: For safe modification of active channel registers both bits should be inactive (except "abort" command).
RXG: Receiving
Transmission Status Register (0x05)
7 NRT3 6 NRT2 5 NRT1 4 NRT0 3 IDT3 2 IDT2 1 IDT1 0 IDT0
* * *
Read only register. Default value after reset: 0x00. The transmission Status register contains the number of retries made up-to-date, according to Table 3, and the channel currently in transmission.
NRT [3:0]: Number of Retries Done in Transmission IDT [3:0]: Channel Number Currently in Transmission Last Message Status Register (0x06)
7 NRTR3 6 NRTR2 5 NRTR1 4 NRTR0 3 IDTR3 2 IDTR2 1 IDTR1 0 IDTR0
* * *
Read only register. Default value after reset: 0x00. This register is the same as the transmission status register. It contains the last identifier number that was successfully transmitted, received or exceeded its retry count. If it was a successful transmission, the number of retries performed can be seen in this register as well.
29
4193G-AUTO-12/04
NRTR [3:0]:
Number of retries done successfully in transmission. In case of reception NRTR[3:0] is undefined. Channel number that was successfully transmitted, received or exceeded its retry count.
IDTR [3:0]: Last Error Status Register (0x07)
7 x
6 BOC
5 BOV
4 x
3 FCSE
2 ACKE
1 CV
0 FV
* * *
Read only register. Default value after reset: 0x00. The Last Error Status Register contains the error code for the last transmission or reception attempt. It is updated after each attempt, i.e. several error codes can be reported during one single transmission (with several retries). When one channel configured in "Reply request" mode has its "received" bit set when it attempts to transmit its request. BOC with the link capability between two channels sharing the same received buffer is set when one channel has already set its "received" bit in its "Message length and status Channel register" and a receive is attempted on the other one.
BOC: Buffer Occupied
* *
BOV: Buffer Overflow
BOV indicates that the buffer length setup in the Channel Status Register was shorter than the number of bytes received plus 1, therefore, some data got lost. One: BOV active Zero: BOV inactive
FCSE: Framing Check Sequence Error
FCSE indicates a mismatch between the FCS received and the FCS calculated One: FCSE active Zero: FCSE inactive ACKE indicates a physical violation or collision on ACK field of the frame when the TSS463 is produced. One: ACKE active Zero: ACKE inactive
ACKE: Acknowledge Error
30
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 17. ACKE Status Bit
DLC: Producer EOD field Expected RAK = 0 Received Received Received RAK* = 1 *RAK: bit of the frame COMMAND field EOD field Expected Received Received Received ACK field ACKE = 0 ACKE = 1 ACKE = 1 ACKE = 1 ACK field ACKE = 0 ACKE = 1 ACKE = 1 ACKE = 1
CV: Code Violation
CV indicates: * either a Manchester code violation (2 identical TS on Manchester bit), or a physical violation (transmitted bit "dominant", received bit "recessive"), on fields ID, COM, DATA and CRC, or a physical violation or collision on field "preamble" and the "recessive" bit of the "Star Sync" field. One: CV active Zero: CV inactive
*
31
4193G-AUTO-12/04
FV: Frame Violation
FV indicates a physical violation or collision on ACK field of the frame when the TSS463 is consumed. One: FV active Zero: FV inactive Figure 18. FV Status Bit
DLC: Consumer EOD Field Expected Received Received Received ACK Field FV = 0 FV = 1 FV = 1 FV = 1
EOD Field Expected Received Received Received
ACK Field FV = 0 FV = 1 FV = 1 FV = 1
Interrupt Status Register (0x09)
7 RST 6 0 5 0 4 TE 3 TOK 2 RE 1 ROK 0 RNOK
* * RST: Reset interrupt
Read only register. Default value after reset: 0x80
RE indicates that the circuit has detected a valid reset command via the RESET pin or the reset command bit GRES. This interrupt cannot be disabled, since its enable bit is set when a reset is detected. This flag is set only when the Max number of transmission (1 + MR [3:0]) is reached with error of transmission. Figure 19. Exceeded Retry with MR[3.0] = 3
TE: Transmit Error Status Flag (or Exceeded Retry)
1st TX
2nd TX
3rd TX
set TE set CHER set CHTx
32
TSS461C
4193G-AUTO-12/04
TSS461C
TOK: Transmit OK Status Flag One: Status flag activated Zero: No status flag. One: Status flag activated Zero: No status flag. One: Status flag activated Zero: No status flag. One: Status flag activated Zero: No status flag.
RE: Receive Error Status Flag
ROK: Receive "with RAK (RAK=1)" OK Status Flag RNOK: Receive "with no RAK (RAK=0)" OK Status Flag Interrupt Enable Register (0x0A)
7 1
6 0
5 0
4 TEE
3 TOKE
2 REE
1 ROKE
0 RNOKE
* *
Read/write register Default value reset: 0x80
On reset the Reset Interrupt Enable bit is set to 1 instead of 0, as the general rule.
Note:
TEE: Transmit Error Enable
One: IT enabled. Zero: IT disabled. One: IT enabled. Zero: IT disabled. One: IT enabled. Zero: IT disabled. One: IT enabled. Zero: IT disabled. One: IT enabled. Zero: IT disabled.
TOKE: Transmission OK Enable
REE: Reception Error Enable
ROKE: Reception "with RAK" OK Enable RNOKE: Reception "with no RAK" OK Enable
Interrupt Reset Register (0x0B)
7 RSTR 6 0 5 0 4 TER 3 TOKR 2 RER 1 ROKR 0 RNOKR
* *
Write only register. Reserved bit: 5 and 6. This bit cannot be set by user; a zero must always be written to this bit.
33
4193G-AUTO-12/04
RSTR: Reset Interrupt Reset
One: Status flag reset Zero: Status flag unchanged One: Status flag reset Zero: Status flag unchanged One: Status flag reset Zero: Status flag unchanged One: Status flag reset Zero: Status flag unchanged One: Status flag reset Zero: Status flag unchanged One: Status flag reset Zero: Status flag unchanged
TER: Transmit Error Status Flag Reset TOKR: Transmit OK Status Flag Reset RER: Receive Error Status Flag Reset ROKR: Receive "with RAK" OK Status Flag Reset RNOKR: Receive "with no RAK" OK Status Flag Reset
Figure 20. Update of the Status Register
EOD SOF BUS 4 TS Set TXG Set RXG ID+COM+DATA+CRC 1 to 2 TS ACK 6 TS Reset RXG, TXG 4 TS
Line Status Register (0x04)
INT
Write "IT Status Register" Write "Last Error Register" Write "Last Message Register" Write "Message Status" Write "Message Length & Status Register"
Channel Registers
There is a total of 14 channel register sets, each occupying 8 bytes for addressing simplicity, integrated into the circuit. Each set contains two 2 x 8-bit registers for the indentifier tag, indentifier mask and command fields plus two 1 x 8-bit registers for DMA pointers and message status. The base_address of each set is: (0x10 + [0x08 * channel_number]). When the TSS461C is reset either via the external reset pin or the general reset command, the channel registers are not affected. For example, on power-up of the circuit, all the channel registers start with random values. Due to this fact, the user should take care to initialize all the channel registers before exiting from idle mode. The easiest way to disable a channel register is to set the received and transmitted bits to 1 in the Message Length & Status Register.
34
TSS461C
4193G-AUTO-12/04
TSS461C
Table 9. Channel Register Sets Map
Channel Number 6 5 4 3 2 1 0 From 0x40 0x38 0x30 0x28 0x20 0x18 0x10 To 0x47 0x3F 0x37 0x2F 0x27 0x1F 0x17 Channel Number 13 12 11 10 9 8 7 From 0x78 0x70 0x68 0x60 0x58 0x50 0x48 To 0x7F 0x77 0x6F 0x67 0x5F 0x57 0x4F
Table 10. Channel Register Set Structure
Reg. Name ID_MASK ID_MASK (no register) (no register) MESS_L/ STA MESS_PTR ID_TAG/ CMD ID_TAG Offset 0x07 0x06 0x05 0x04 0x03 0x02 0x01 0x00 DRACK ID_T [3: 0] x x x x x x M_L [4:0] M_P [6:0] EXT ID_T [11:4] RAK RNW RTR Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 x ID_M [11:4] x x x x x x CHER x x CHTx x x CHRx Bit 2 x Bit 1 x Bit 0 x
ID_M [3:0]
Identifier Tag and Command Registers
The identifier tag and command registers are located at the base_address and base_address + 1. It allows the user to specify the full 12-bit identifier field of the ISO standard and the 4-bit command.
7 ID_T 3 6 ID_T 2 5 ID_T 1 4 ID_T 0 3 EXT 2 RAK 1 RNW 0 RTR base_address + 0x01
7 ID_T 11
6 ID_T 10
5 ID_T 9
4 ID_T 8
3 ID_T 7
2 ID_T 6
1 ID_T 5
0 ID_T 4 base_address + 0x00
*
Read/Write registers.
35
4193G-AUTO-12/04
ID_T [11:0]: Identifier Tag
Upon a reception hit (i.e, a good comparison between the identifier received and an identifier specified, taking the comparison mask into account, as well as a status and command indicating a message to be received, the identifier tag bits value will be rewritten with the identifier bits actually received. No comparison will be done on the command bits, except on EXT bit. The RAK, RNW and RTR bits will be written into the first byte of the Message upon a reception hit. The RNW and RTR bits, as well as the status bits in the length and status register, must be in a valid position for reception or transmission. If not, the message corresponding to this identifier is considered as inactive or invalid. The way of knowing if an acknowledge sequence was requested or not is to check the first byte of the Message.
EXT, RAK, RNW & RTR: (See Section "Retries, Rearbitrate and Abort")
Message Pointer Register
The message pointer register at address (base_address + 0x02) is 8 bits wide. It indicates where, in the Message DATA RAM area, the message buffer is located.
7 DRAK 6 M_P 6 5 M_P 5 4 M_P 4 3 M_P 3 2 M_P 2 1 M_P 1 0 M_P 0 base_address + 0x02
*
Read/Write register
DRAK: Disable RAK (Used in 'Spy Mode')
In reception: whatever is the RAK bit of the incoming valid frame, no ACK answer will be set. If the message was successfully received, an IT is set (ROK or RNOK). In transmission: no action. One: disable active, 'spy' mode. Zero: disable inactive, normal operation.
M_P [6:0]: Message Pointer
Since the Message DATA RAM area base address is 0x80, the value in this register is the offset from that address. If the message buffer length value is illegal (i.e. zero), this register is redefined as being a link pointer, thus containing the channel number of the channel that contains the actual message pointer, message length and received status. However, the identifier, mask, error and transmitted status used will be the originally matched channel. In any case, if a link is intended, the three high bits of M_P [6:0] should be set to 0. This allows several channels to use the same actual reception buffer in Message DATA RAM, thus diminishing the memory usage. Note that only 1 level of link is supported.
36
TSS461C
4193G-AUTO-12/04
TSS461C
Message Length And Status Register The message length and status register at address (base_address + 0x03) is also 8 bits wide. It indicates the length reserved for the message in the Message DATA RAM area.
7 M_L 4 6 M_L 3 5 M_L 2 4 M_L 1 3 M_L 0 2 CHER 1 CHTx 0 CHRx base_address + 0x03
*
Read/Write register.
M_L [4:0]: Message Length
The 5 high bits of this register allow the user to specify either the length of the message to be transmitted, or the maximum length of a message receivable in the pointed reception buffer. Note that the first byte in this register does not contain data, but the length of the message received. This implies that the length value has to be equal to or greater than the maximum length of a message to be received in this buffer (or the length of a message to be transmitted) plus 1. Thus allowing a maximum length of 30 bytes and a minimum length of 0 byte. If the value of this field is illegal (i.e 0x00) then this message pointer is defined as being a link (see section "Message Pointer Register" and Section "Linked Channels").
M_L [4:0] = 0x00 M_L [4:0] = 0x01 M_L [4:0] = 0x02 ------M_L [4:0] = 0x1D M_L [4:0] = 0x1E M_L [4:0] = 0x1F Linked channel Frame with no DATA field (*) Frame with 1 DATA byte ---------------------Frame with 28 DATA bytes Frame with 29 DATA bytes Frame with 30 DATA bytes
(*) Different of a reply request frame with no in-frame reply (deferred reply).
CHER: Channel Error Status and Abort Command
As status, this bit is set by the TSS461C when error occurs in transmission or on a received frame. The user must reset it. To abort the transmission defined in the channel, this bit can be set to1 by the user (see Section "Retries, Rearbitrate and Abort" and Section "Abort").
CHTx: Channel Transmitted and Transmit Enable Command
37
4193G-AUTO-12/04
CHRx: Channel Received and Receive Enable Command
The two low order bits of this register contain the message status. Together with the RNW and RTR bits of the command register (base_address + 0x01), they define the message type of this channel (seeSection "Messages Types"). As a general rule (see Section "Abort"), the status bits are only set by the TSS461C, so the user must reset them to perform a transmission (CHTx) or/and a reception (CHRx). The received and transmitted bits are only set if the corresponding frame is without errors or if the retry count has been exceeded. The Identifier Mask registers (base_address + 0x06 and base_address + 0x07) allow bitwise masking of the comparison between the identifier received and the identifier specified.
7 ID_M 3 6 ID_M 2 5 ID_M 1 4 ID_M 0 3 x 2 x 1 x 0 x
Identifier Mask Registers
7 ID_M 11
6 ID_M 10
5 ID_M 9
4 ID_M 8
3 ID_M 7
2 ID_M 6
1 ID_M 5
0 ID_M 4
* ID_M [11:0]: Identifier Mask
Read/Write registers
A value of 1 indicates comparison enabled. A value of 0 indicates comparison disabled.
38
TSS461C
4193G-AUTO-12/04
TSS461C
Mailbox
The mailbox contains all the messages received or to be transmitted. Each messages is link to a channel. The Mailbox RAM area has 128 bytes and is mapped from 0x80 to 0xFF (see Section "Mapping"). The message (or message buffer) is composed of: * * 1 byte of message status (only used in receiving) Bytes of data. These data are the bytes of the DATA field of the frame with the same organization.
The message is pointed by the Message Pointer Register of the channel, the length of the message is given by the Message Length & Status Register of the channel (Section "Message Pointer Register" and Section "Message Length And Status Register"). This area is a pure RAM, it contains a random value after reset. Figure 21. Message Buffer Structure for Reception
Message Length & Status Register M_L [4..0] CHER CHTx CHRx Message Pointer Register DRAK M_P [6..0]
( M_L >= n + 2 )
Message Received DATA n M_P + 0x80 + n + 2
received DATA 0 RAK RNW RTR M_L [4..0] = n+1 received received received received M_P + 0x80
EXT RAK RNW
RTR
EOD
SOF
ID [11..0]
DATA 0
DATA n
FCS
ACK
EOF
Note:
Received DATA Frame, immediate or deffered reply
39
4193G-AUTO-12/04
Figure 22. Message Buffer Structure for Transmission
Message Length & Status Register
M_L [4..0] CHER CHTx CHRx
Message Pointer Register
DRAK M_P [6..0]
( M_L >= n + 2 )
Message
transmitted
DATA n
M_P + 0x80 + n + 2
transmitted
DATA 0
M_P + 0x80
(nothing)
RNW
RTR
EOD
SOF
ID [11..0]
EXT RAK
DATA 0
DATA n
FCS
ACK
2
EOF
Transmitted DATA Frame
Message Status (Pointed by: Message Pointer Register)
7 RRAK 6 RRNW 5 RRTR 4 RM_L4 3 RM_L3 1 RM_L1 0 RM_L0
RM_L2
(no significant value in case of message to be transmitted)
RRAK: Received RAK Bit
This bit is the RAK bit coming from the COM field of the received frame.
RRNW: Received RNW Bit
This bit is the RNW bit coming from the COM field of the received frame.
RRTR: Received RTR Bit
This bit is the RTR bit coming from the COM field of the received frame.
RM_L[4:0]: Message Length of the Received Frame
If the DATA field of the received frame included DATA0 to DATAn, RM_L[4:0] = n+1, even if the reserved length (Message Length & Status Register) is larger.
40
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 23. Message Status Updating
Frame Type Node x I, P Data Frame Communication Node A C RAK RNW RTR Length Message Status on Node A after IT(*)
Immediate Reply
I, C
P RAK RNW RTR Previous Value
Deferred Reply
I, C
P RAK RNW RTR Previous Value
C Data Frame
I, P previous values
Immediate Reply
P
I, C RAK RNW RTR Length
Deferred Reply
P
I, C RAK RNW RTR Length
P: Producer
I: Initiator
C: Consumer
(*) After IT ROK or RNOK. In case of IT RE, the values can be erroneous.
Message Data (String Pointed by: Message Pointer Register + 1)
7 6 5 4 DATAn --------DATA0 ------ - --3 2 1 0
DATA0 is the first received (or transmitted) byte, DATAn is the last one.
Notes: 1. If the length reserved (in the message length & status register) for an incoming frame is 2 bytes greater or more, the TSS461C will write the 2 bytes of the CRC field in the message string just after DATAn. Because the VAN frame does not contain a message length, the only way for the component to know the length of the DATA field is either the message length register value, or the EOD field detection. When the reserved length is too large, at the moment when it detects the EOD, the TSS461C has already written the 2 bytes of the CRC field, considering these bytes as normal DATA. 2. The Mailbox RAM area is a circular buffer. The next location after 0xFF is 0x80.
41
4193G-AUTO-12/04
Messages Types
There are 5 basic message types defined in the TSS461C. Two of them (transmit and receive message types) correspond to the normal frame, and the rest correspond to the different versions of reply frames.
Transmit Message RNW Initial Setup After Transmission 0 0 RTR 0 0 CHTx 0 1 CHRx Don't Care Unchanged
To transmit a normal data frame on the VAN bus, the user must program an identifier as a Transmit Message. The TSS461C will then transmit this message on the bus until it has succeeded or the retry count is exceeded.
Receive Message RNW Initial Setup After Transmission 0 0 RTR 1 1 CHTx Don't Care Unchanged CHRx 0 1
The opposite of the transmit message type is the Receive Message type. This message type will not generate any frames on the bus. Instead, it will listen to the bus until a frame passes that matches its identifier, with the mask taken into account, and then receive the data in that frame. The data received will be stored in the message buffer and the length of the message received is stored in the first byte of the message buffer. The actual identifier received is stored in the identifier register itself. This identifier may differ from the identifier specified in the register due to the effect of the mask register. Normally, this should not interfere with the next identifier comparison since the bits that may differ are masked via the mask register.
Reply Request Message RNW Initial Setup After Transmission (Waiting for reply) After Reception (of reply) 1 1 RTR 1 1 CHTx 0 1 CHRx 0 0
1
1
1
1
The Reply Request Message type is a demand to transmit on the VAN bus a reply request. When this message type is programmed, three things can happen. First, no other modules on the bus responded with an in-frame reply, in this case the TSS461C will set the message type to the after transmission state. When this message type is programmed, the TSS461C will listen on the bus for a deferred reply frame matching this identifier, without transmitting the reply request.
42
TSS461C
4193G-AUTO-12/04
TSS461C
Second, another module on the bus replies with an in-frame reply. In this case the message type will pass immediately into the after reception state, without passing the after transmission state.
Reply Request Message Without Transmission RNW Initial Setup After Reception 1 1 RTR 1 1 CHTx Don't Care Unchanged CHRx 0 1
Third, the TSS461C has not yet started to transmit the reply request, when another module either requests a reply, and gets it, or transmits a deferred reply. Warning! This should be avoided as it may result in an illegal message type (Illegal reply Request).
Immediate Reply Message RNW Initial Setup After Transmission 1 1 RTR 0 0 CHTx 0 1 CHRx 0 1
The immediate Reply Message will attempt to transmit an in-frame reply, using the data in the message buffer. A deferred Reply Message is shown below.
Deferred Reply Message RNW Initial Setup After Reception (of Reply Request) 1 1 RTR 0 0 CHTx 0 1 CHRx 1 1
This message type will immediately transmit a deferred reply frame.
Reply Request Detection Message RNW Initial Setup After Reception 1 1 RTR 0 0 CHTx 1 1 CHRx 0 1
Finally, there is the Reply Request Detector Message type. Its purpose is to receive a reply request frame and notify the processor, without transmitting an in-frame reply.
Inactive Message RNW Recommended After Transmission After Reception Illegal Reply Request Don't Care 0 0 1 RTR Don't Care 0 1 1 CHTx 1 1 Don't Care 0 CHRx 1 Don't care 1 1
The table above shows all inactive messages types. The last combination will transmit a reply request, but will not receive the reply since its buffer is tagged as occupied.
43
4193G-AUTO-12/04
Priority Among the Different Channels
The priority handling on the VAN bus is already explained in the Line Interface section. The priorities for the messages in the TSS461C is, however, slightly different. For instance, it's possible that an identifier matches two or more of the identifiers programmed into the registers. In this case, it is the lowest identifier number that has priority. i.e., if both identifier 5 and 10 match the identifier received, it is the identifier 5 that will receive the message. However, since the identifier 5 will become an inactive message when it has received the frame, the next time the same identifier is seen on the bus, the corresponding data will be received by identifier 10. The same is valid for messages to be transmitted, i.e., if two or more messages are ready to be transmitted, it is the one with the lowest identifier number that will get priority.
44
TSS461C
4193G-AUTO-12/04
TSS461C
Retries, Rearbitrate and Abort
Retries and rearbitrate commands are located, in the Transmit Control Register and in the Command Register, respectively. An abort command is located in each channel register set, in the Message Length & Status Register (base_address + 0x03). These three commands are available only when the TSS461C is producer. Figure 24. Transmit Function Activate
Ch. Enabled in Xmit Mode? yes Disable of current Ch. Select the lowest Ch. number and load"Max - retries" yes Abort activated on current Ch.? no
no
Wait for bus free (EOF+IFS= 12 Timeslots) Decrement retry counter Transmit frame and wait for the end
abort
Abort required on current Ch. rearbitrate? no
rearbitrate
yes
Retry needed?
no
Retries
The purpose of retries feature is to provide, the capability of retrying a transmit request in case of failure, when a node tries to reach another node, either on normal DATA frame or on REPLY REQUEST frame. The maximum number of retries is programmable through MR[3:0] of the Transmit Control Register (0x01). When a channel is enable - bit CHTx = 0 of Message Length & Status Register, a 4-bit counter is loaded with MR[3:0]. At each attempt, this counter will be countdown. To 0, an IT TE is set in the Interrupt Status Register (0x09), and the transmission is stopped. MR[3:0] = 1 indicates 1 retry, hence 2 transmission attempts will be performed (see Table 4). The number of retries performed, as well as the current channel number associated, can be read in the Transmission Status Register (0x05).
45
4193G-AUTO-12/04
The Last Error Status Register (0x07) informs about the trouble encountered: * Failure cases: - - - * Code viol (CV error bit) Acknowledge error (ACKE error bit) CRC error (FCSE error bit)
It should be noticed that contention is considered as normal CSMA/CD protocol and, therefore, is not taken into account in failure cases. So, an "infinite" number of attempts can be performed if bus contention occurs continuously.
There is only one retry counter for all channels. When the user writes the Max_Retries value, all channels start their transmission with this parameter.
Rearbitrate
The purpose of rearbitrate feature is to postpone a channel already in transmission in order to authorize an higher priority (see Section "Priority Among the Different Channels") message to be transmit. * * * * Max_retries = 1 (2 transmissions attempts). If Ch8 is in a the retry loop and the user wants to transmit the Ch5 without waiting the end of the loop, the user can use the rearbitrate command. Then, the TSS461C will wait the end of the current transmission, reload the retries counter and enable the Ch5 to transmit. At the end of this transmission Ch5, either when the attempt is successful or either when the exceeded retry count is reached, the retries counter is reloaded and the transmission is activated for the Ch8 again.
Typical Example
Figure 25. Rearbitrate Example
Ex: FCS Error * (not seen by application)
Set CHTx/Ch5 & ITROK
(Load Max-Retries)
(Load Max-retries)
Delay V iol
VCC VCC EOF+IFS
(Load Max-retries)
Rearbitrate (Activate Ch5)
Set CHER & CHTx /Ch8, and set IT TE Ex: set FSCE status bit
Delay Viol
Ex: FCS Error (not seen by application)
stand-by
Delay Viol
Second attempt Xmit Ch8
First attempt Xmit Ch8
First attempt Xmit Ch8
(Retries - 1)
Xmit Ch5
EOF+IFS: 8 + 4 T imeslots Delay Viol: 12 T imeslots
* (not seen by application means no IT generation)
46
TSS461C
4193G-AUTO-12/04
TSS461C
Figure 26. Idle and Rearbitrate Example
Set CHTx/Ch5 & ITROK
(Load Max-retries)
(Load Max-retries)
* (not seen by application)
(Load Max-retries)
Idle command
Rearbitrate (Activate Ch5)
Set CHER & CHTx /Ch8, and set IT TE Ex: set FSCE status bit
Delay Viol
(not seen by application)
Ex: FCS Error
Ex: FCS Error
Idle
Delay
Viol
EOF+IFS
Delay Viol
Second Attempt Xmit Ch8
First Attempt Xmit Ch8
First Attempt Xmit Ch8
(Retries - 1)
Xmit Ch5
EOF+IFS: 8 + 4 T imeslots Delay Viol: 12 T imeslots
* (not seen by application means no IT generation)
If the user sets the idle bit anywhere (after rearbitrate), the idle mode is entered only at the end of all the transmit attempts (for more information about idle command, see Section "Activate, Idle and Sleep Modes"). Disable Channel After Rearbitrate Figure 27. Disable Channel After Rearbitrate Example
(Load Max-retries)
(Load Max-retries)
Disable Ch8(*)
(not seen by application)
Ex: FCS Error
(Activate Ch5)
Rearbitrate
(not seen by application)
Delay Viol
Ex: ACK Error
Set CHER & CHTx /Ch5, and set IT TE Ex: setACKE status bit
Delay Viol stand-by
(Retries - 1) KO Second attempt Xmit Ch5 Set CHTx/Ch5 & ITTOK
Delay Viol
First attempt Xmit Ch8
First attempt Xmit Ch5
OK
EOF+IFS
stand-by
EOF+IFS: 8 + 4 T imeslots Delay Viol: 12 T imeslots
(1) The disable is applied setting the CHTx/Ch8 bit to 1.
Note:
1. In this case, the TSS461C completes the current attempt (Ch8) and lets the transmission go to the new channel (Ch5 if validated); otherwise, it stops all attempts on the current channel.
47
4193G-AUTO-12/04
Abort
An abort command is dedicated to channels already enabled in transmission or in-frame response. For example, this command can be used to break the retry procedure on one channel. Abort channel is done by setting the Error bit (CHER) in the Message Length & Status Register (base_address + 0x02). This command is taken into account if the channel aborted is not transmitted. When this abort command is really done, the TSS461C set to 1 the Transmitted bit (CHTx) of the Message Length & Status Register. The abort mechanism is integrated into the transmit function. This means, abort, priority and retries live together in the transmit function.
Figure 28. Abort Example
IT ROK CHTx Setor CHER/Ch6 &or IT RE
Activate Abort Ch0 (before Xmit) Set CHTx/Ch0
Abort Ch13 (before Xmit)
Set CHTx/Ch6 & ITROK if Successful
Set CHTx/Ch6 & ITROK if Successful
Abort Ch4 (during Xmit)
Set CHTx/Ch4 &ITROK
Ch s Initialization
12 Timeslots
Xmit Ch6 if Previously Fail
48
TSS461C
4193G-AUTO-12/04
Xmit Ch6 if Previously Fail
Xmit Ch4
Xmit Ch6
Set CHTx/Ch13
Reset
TSS461C
Activate, Idle and Sleep Modes
Idle and Activate Commands
Sleep, idle and activate commands are located in the Command Register (0x03). These three commands are general commands for the TSS461C. After reset, the TSS461C starts in idle mode. In this mode, the oscillator operates (CKOUT pin active) but the circuit cannot transmit or receive anything on the VAN bus. The TxD output (pin 18) is in three-state mode, a pull-up resistor must be provided externally or by the line driver to avoid floating state on the VAN bus. To activate the TSS461C, the user must set the activate bit (ACTI) and reset the idle bit (IDLE). Figure 29. Idle and Activate Timings
Idle Mode
Activate Mode
SOF
RxD After Reset TxD 3 TS (max)
Activate Command
SOF
8 TS 12 TS TS: Timeslot Period
Activate Mode
EOD FCS ACK
Idle Mode
RxD
Idle Command
INT 4 TS 5 TS
In both cases, the idle state can be verified by reading the Line Status register (0x04).
Sleep Command
If the user sets the sleep bit (SLEEP), the TSS461C enters in sleep mode, whatever are the values of activate and idle bits. All non-user registers are setup to reduce the power consumption and the internal oscillator is immediately stopped. However, all user registers (accessible by P bus) are always available by the user To exit from this mode, the user must set either the idle bit or the activate bit. In a typical application (Figure 1) using the CKOUT feature (pin 12), if the TSS461C is put in sleep mode, the clock provided to the microcontroller is stopped. So, the system does not run and the only way to awake this application is an external reset.
49
4193G-AUTO-12/04
Linked Channels
The linkage feature allows two channels to share the same Message area, the message pointer and the message length assumes the following property: * * * Zero value as message length (M_L [4:0] - base_address + 0x03) declares the channel linked to another channel. The number of this other channel is defined in the message pointer field (M_P [6:0] - base_address + 0x02). The pointer and the length values for the Message area are defined only once time, in the register set of this other Channel.
Only one level of linkage can be created. For example, (see Figure 29) a Channel k can be linked to the Channel i but not to Channel j, already defined as linked to Channel i. All the others can be different between the two channels, for example the ID_Tag. Figure 30. Linkage Mechanism
The Channel j linked
....
Channel i and j
share the same Message area
to the Channel i
ID_Mask j (lsb)
--- Channel j ---
ID_Mask j (msb)
--- Message forChannels i & j ---
0x00
DRAK ID_Tag j (lsb)
CHER CHTx CHRx
DATA n
i
EXT RAK RNW RTR ID_Tag j (msb)
--- Channel i ---
ID_Mask i (lsb) ID_Mask i (msb)
DRAK
Mess_Len = n+2CHER CHTx CHRx Mess_Ptr
ID_Tag i (lsb) EXT RAK RNW RTR ID_Tag i (msb)
Length = n+2 DATA 0 Message Status
This Message Area sharing permits either optimizing the allocation of the 128 bytes of DATA, performing some special communications between the different nodes of the network. 50
TSS461C
4193G-AUTO-12/04
TSS461C
Electrical Characteristics
Absolute Maximum Ratings
Ambient temperature under Bias: A = Automotive .................................................-40C to 125C Storage Temperature ........................................-65C to 150C Voltage on VCC to VSS .......................................... -0.5 to +7.0V Voltage on any Pin to VSS ........................ -0.5V to VCC + 0.5V Note: Stresses at or above those listed under "Absolute Maximum Ratings" may cause permanent damage to the device. This is a stress rating only and functional operation of the device at these or any other conditions exceeding those indicated in the operational sections of this specification is not implied. Exposure to absolute maximum rating conditions may affect device reliability.
DC Characteristics
Symbol VIL VIH VIL1 VIH1 VOL VOH IL RPD CIO ICCSB Parameter
TA = -40C to 125C; VCC = 5V 10%; VSS = 0V
Min -0.5 Max 0.8 Type V Test Conditions
Input Low Voltage (except RESET and XTAL1) Input High Voltage (except RESET and XTAL1) Input Low Voltage (RESET and XTAL1) Input High Voltage (RESET and XTAL1) Output Low Voltage Output High Voltage Input Leakage Current Input Pull-down Resistor I/O Buffer Capacitance Power Supply Current Sleep Mode Power Supply Current Idle or Active Mode
2.0 -0.5 0.7 VCC
VCC+0.5 0.3*VCC VCC+0.5 0.4
V V V V IOL = 3.2 mA, VCC min IOH = -3.2 mA, VCC min See Figure 2
2.4 +5 110 10 50 4 15 A k pF A mA mA
0 < VIN < VCC 0 < VIN < VCC Not tested (Note 1) (Notes 2, 4) (Notes 3, 4)
ICCOP
Notes:
1. 2. 3. 4. 5.
Sleep Mode ICCSB is measured according to Figure 31 with a VSS Clock Signal. Active mode ICCOP is measured at: XTAL = 1 MHz clock, VAN speed rate = 62.5 KTS/s. Active mode ICCOP is measured at: XTAL = 16 MHz clock, VAN speed rate = 250 KTS/s. ICC is a function of the Clock Frequency. Figure 32 displays a graph showing ICC versus Clock frequency. RESET, RxD0, RxD1, RxD2 inputs.
51
4193G-AUTO-12/04
Figure 31. ICC
Icc
TXD CLOCK SIGNAL N.C.
Figure 32. ICC versus Clock Frequency at 250 KTimeslot/s
mA
12
11.5
11
10.5
MHz 2 4 6 8
52
TSS461C
4193G-AUTO-12/04
TSS461C
AC Characteristics
Microprocessor Interface TA = -40C to 125C; VCC = 5V 10%; VSS = 0V
Symbol TRESET 1 2 3 4 5 6 7 8 9 10 11 TLHLL TAVLL TLLAX TAVWL TDVWH TWHDX TWHLH TRLDV TRHDZ TWHRLIZ TIZIL Characteristic RESET High Pulse Width (For Power-up Reset) ALE High Pulse Width Address Valid to ALE Low Setup Time ALE Low to Address Invalid Hold Time Address Valid to Command Active Time Data Valid to Write Inactive Setup Time Write Inactive to Data Invalid Hold Time Write Inactive to ALE High Recovery Time Read Active to Data Valid Access Time Read Inactive to Data Float Time Write Inactive or Read Active to IRQ Float Time IRQ Float Pulse Width 2 Min 15 10 10 10 20 10 12 20 110 20 90 20 Max Unit ns ns ns ns ns ns ns ns ns ns ns ns
53
4193G-AUTO-12/04
Oscillator Characteristics
Figure 33. C2 versus Frequency pF
200
100 33
1 Note:
2
4
8
MHz
C1 (no capacitance needed) see Figure 1.
External Clock Drive Characteristics (XTAL1)
Symbol TCHCH TCHCX TCLCX TCLCH TCHCL
Parameter Oscillator Period High Time Low Time Rise Time Fall Time
Min 120 20 20
Max
Unit ns ns ns
20 20
ns ns
t CHCL
t CLCH
V IH V IL V IL V IH
XTAL1
V IH
t CHCX t CHCH
t CLCX
54
TSS461C
4193G-AUTO-12/04
TSS461C
Packaging Information
SO24
24
SO A A1 B C D E e H h L N a 2.35 0.10 0.35 0.23 15.20 7.40 1.27 10.00 0.25 0.40
MM 2.65 0.30 0.49 0.32 15.60 7.60 BSC 10.65 0.75 1.27 24 0 0.093 0.004 0.014 0.009 0.599 0.291 0.050 0.394 0.010 0.016
INCH 0.104 0.012 0.019 0.013 0.614 0.299 BSC 0.419 0.029 0.050 24 0
55
4193G-AUTO-12/04
Ordering Information
Part Number TSS461C TSS461C:R TSS461C-TDRZ(1) Supply Voltage 5V +10% 5V +10% 5V +10% Temperature Range -40C - +125C -40C - +125C -40C - +125C Package SO24 SO24 SO24 Packing Tube Tape & Reel Tube
Note:
1. These products are available in ROHS version.
56
TSS461C
4193G-AUTO-12/04
Atmel Corporation
2325 Orchard Parkway San Jose, CA 95131 Tel: 1(408) 441-0311 Fax: 1(408) 487-2600
Atmel Operations
Memory
2325 Orchard Parkway San Jose, CA 95131 Tel: 1(408) 441-0311 Fax: 1(408) 436-4314
RF/Automotive
Theresienstrasse 2 Postfach 3535 74025 Heilbronn, Germany Tel: (49) 71-31-67-0 Fax: (49) 71-31-67-2340 1150 East Cheyenne Mtn. Blvd. Colorado Springs, CO 80906 Tel: 1(719) 576-3300 Fax: 1(719) 540-1759
Regional Headquarters
Europe
Atmel Sarl Route des Arsenaux 41 Case Postale 80 CH-1705 Fribourg Switzerland Tel: (41) 26-426-5555 Fax: (41) 26-426-5500
Microcontrollers
2325 Orchard Parkway San Jose, CA 95131 Tel: 1(408) 441-0311 Fax: 1(408) 436-4314 La Chantrerie BP 70602 44306 Nantes Cedex 3, France Tel: (33) 2-40-18-18-18 Fax: (33) 2-40-18-19-60
Biometrics/Imaging/Hi-Rel MPU/ High Speed Converters/RF Datacom
Avenue de Rochepleine BP 123 38521 Saint-Egreve Cedex, France Tel: (33) 4-76-58-30-00 Fax: (33) 4-76-58-34-80
Asia
Room 1219 Chinachem Golden Plaza 77 Mody Road Tsimshatsui East Kowloon Hong Kong Tel: (852) 2721-9778 Fax: (852) 2722-1369
ASIC/ASSP/Smart Cards
Zone Industrielle 13106 Rousset Cedex, France Tel: (33) 4-42-53-60-00 Fax: (33) 4-42-53-60-01 1150 East Cheyenne Mtn. Blvd. Colorado Springs, CO 80906 Tel: 1(719) 576-3300 Fax: 1(719) 540-1759 Scottish Enterprise Technology Park Maxwell Building East Kilbride G75 0QR, Scotland Tel: (44) 1355-803-000 Fax: (44) 1355-242-743
Japan
9F, Tonetsu Shinkawa Bldg. 1-24-8 Shinkawa Chuo-ku, Tokyo 104-0033 Japan Tel: (81) 3-3523-3551 Fax: (81) 3-3523-7581
e-mail
literature@atmel.com
Web Site
http://www.atmel.com
Disclaimer: Atmel Corporation makes no warranty for the use of its products, other than those expressly contained in the Company's standard warranty which is detailed in Atmel's Terms and Conditions located on the Company's web site. The Company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and does not make any commitment to update the information contained herein. No licenses to patents or other intellectual property of Atmel are granted by the Company in connection with the sale of Atmel products, expressly or by implication. Atmel's products are not authorized for use as critical components in life support devices or systems. (c) Atmel Corporation 2004. All rights reserved. Atmel(R), logo and combinations thereof are registered trademarks, and Everywhere You Are(SM) are the trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others.
Printed on recycled paper.
4193G-AUTO-12/04 /xM


▲Up To Search▲   

 
Price & Availability of TSS461C04

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X